Skip to content

Fix header formatting: shorten nav title and prevent nav items from w…#19441

Open
Nazim-fad wants to merge 1 commit intopytorch:mainfrom
Nazim-fad:fix-header-formatting
Open

Fix header formatting: shorten nav title and prevent nav items from w…#19441
Nazim-fad wants to merge 1 commit intopytorch:mainfrom
Nazim-fad:fix-header-formatting

Conversation

@Nazim-fad
Copy link
Copy Markdown

@Nazim-fad Nazim-fad commented May 9, 2026

Summary

Fix header formatting #19347

The navigation bar header had inconsistent spacing due to nav items wrapping to multiple lines on most screens.

Changes:

  • Shortened "Find Your Path in ExecuTorch" → "Find Your Path" in user-pathways.md
  • Added docs/source/_static/navbar.css with white-space: nowrap to prevent nav items from wrapping in the header
  • Registered navbar.css in conf.py via html_css_files

Test plan

Built docs locally and previewed:
Capture d’écran 2026-05-09 190234

Ran lintrunner on changed files

cc @GregoryComer @AlannaBurke @mergennachin

@Nazim-fad Nazim-fad requested a review from mergennachin as a code owner May 9, 2026 18:21
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented May 9, 2026

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/19441

Note: Links to docs will display an error until the docs builds have been completed.

⚠️ 11 Awaiting Approval, 1 Unrelated Failure

As of commit a9e7f64 with merge base a49171d (image):

AWAITING APPROVAL - The following workflows need approval before CI can run:

FLAKY - The following job failed but was likely due to flakiness present on trunk:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented May 9, 2026

Hi @Nazim-fad!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@pytorch-bot pytorch-bot Bot added the release notes: none Do not include this in the release notes label May 9, 2026
@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented May 9, 2026

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label May 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. release notes: none Do not include this in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants